Release notes display cleanup#1373
Conversation
Point validate-docs-site at beck/sc-16656/renew-release-notes-process so staging previews include in-progress release notes CSS and listings. Remove ref before merge.
Merge guard — remove
|
Closes missing ::: so Quarto validate-docs-site CI no longer warns. Co-authored-by: Cursor <cursoragent@cursor.com>
PR SummaryThis PR introduces several UI enhancements and content updates across the site. The changes can be summarized in two parts:
Overall, these changes improve responsiveness and the visual layout of the academy features section while also refining the navigation and structure of the release notes section. Test Suggestions
|
Validate docs site✓ INFO: A live preview of the docs site is available — Open the preview |
Lighthouse check results✓ INFO: Average accessibility score is 0.92 (required: ≥0.9) — View the workflow run Audit mode: changed pages (2 URL(s)) Show Lighthouse scoresCommit SHA: f4b365d For a thorough audit, run the Lighthouse check workflow manually (Actions → Lighthouse check → Run workflow) with depth 0–2, or add the
|
Pull Request Description
What and why?
Simplifies the public releases hub so current releases, feature highlights, and the historical archive are easier to scan.
Documentation / index
#releasesanchor on the home page Latest Features section for deep links.academy-features-row) so Academy and Latest Features align evenly on desktop and stack on mobile instead of having weird extra paddingAll releases
25.03and earlier vs25.04+)How to test
Click on the live previews:
Confirm the four-tile current-releases grid, six-row highlights table, and archive copy render without listing errors.
What needs special review?
Dependencies, breaking changes, and deployment notes
Warning
Remove the
ref:to the pairedrelease-notesbranch under the release notes step invalidate-docs-site.yamlbefore merging.Related epic PRs
Release notes
n/a
Checklist